require CTFE to detect UB #60
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
RalfJung
commented
Oct 31, 2020
| [UB]: https://doc.rust-lang.org/reference/behavior-considered-undefined.html | ||
|
|
||
| # Reference-level explanation | ||
| [reference-level-explanation]: #reference-level-explanation |
Member
Author
There was a problem hiding this comment.
As usual I have no idea how to split the RFC intention across "guide-level" and "reference-level" explanation.^^ That separation makes very little sense to me, for most of the RFCs that I end up writing...
oli-obk
approved these changes
Nov 1, 2020
Contributor
oli-obk
left a comment
oli-obk
left a comment
There was a problem hiding this comment.
non-detected UB, CTFE continues in a reasonable way, instead of producing an arbitrary result.
yes, we should not permit CTFE to explicitly create bogus values on UB when, in order to do that, it would need to detect the UB and choose to create a bogus value. If UB is detected, interpretation must be aborted. If UB is not detected, CTFE continues in a reasonable way.
Co-authored-by: Oli Scherer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is what @oli-obk and me agreed on here, except I went one step further and now require that for non-detected UB, CTFE continues in a reasonable way, instead of producing an arbitrary result. Once we keep the unoptimized MIR around, that is cheap to do. For example, this means that when the code violates alignment, CTFE must either raise an error or continue as if the pointer was actually well-aligned (and perform the appropriate load from the given region of memory). The previous wording would have allowed CTFE to return
Undefwhen loading from an unaligned pointer -- I cannot see a good reason why we would permit CTFE to do that.